@dkotter @jeffpaul I'm stuck making the tests work after this change - by setting the preview to default to true, the winamp canvas element is blocking cypress from clicking the publish button. The error message suggests forcing the click, but the click in question is handled upstream by the cypress utils. Additionally, this could be hinting at an accessibility issue that might make us reconsider showing the preview by default. Any thoughts here?

  1) Admin can publish posts with winamp block
       Can insert the block and publish the post:
     CypressError: Timed out retrying after 4050ms: `cy.click()` failed because this element:

`<button type="button" aria-disabled="false" class="components-button editor-post-publish-button editor-post-publish-button__button is-primary">Publish</button>`

is being covered by another element:

`<canvas height="343" width="431" style="height: 100%; width: 100%; display: block;"></canvas>`

Fix this problem, or use {force: true} to disable error checking.

https://on.cypress.io/element-cannot-be-interacted-with

A couple concerns I have:

1. The issue with the preview, which I'm assuming is what's causing the test failures, is it renders in a fixed position, so as you scroll in the editor, the preview moves with you and covers everything else. This was a problem I was never able to solve in the initial build which is one reason why we don't show the preview by default. It doesn't work this way on the front-end so I'm assuming something about the Block Editor (maybe some other conflicting styles) causes it to function this way.
2. You can't add new media files in the preview mode. Just my personal opinion here but by rendering the preview by default anytime there's audio files, you have to switch that off to add additional files. And with that option now in the sidebar, it makes it harder to do that

I think we need to solve the fixed positioning issues if we want to have the preview on by default. Otherwise it's pretty annoying, especially if you have additional content in the post besides just this block, as it ends up covering everything.

@dkotter I took a pass at making what I feel is a pretty good UX solution here. The approach is a little heavy handed, but the webamp library is pretty limited in terms of what we're trying to accomplish. The updates now move the webamp component inside the block markup and positions it neatly, which a.) activates the block when the user interacts with the winamp component and b.) looks a lot nicer than the previous position which was just randomly floating on the page. Check out the gif in the PR description and let me know what you think. cc @jeffpaul

This looks good to me! Nice work here @psorensen